preserve daemon sessions across self-updates - #369

Note

Medium Risk
Touches core daemon lifecycle, socket ownership, and client reconnect paths where races could still affect session restore or stale socket handling; behavior is heavily tested but production update flows are critical.

Overview
Self-updates should no longer drop attached sessions when old and replacement daemons overlap during Unix socket cleanup. Shutdown now broadcasts daemon_closing with reason update or shutdown, and clients use that signal instead of guessing from a bare socket close.

DaemonAgentConnection automatically reconnects after an update restart: it re-lists sessions, re-attaches by session file/id, and emits session_replaced on success. Failures surface guided errors (session id, file path, daemon log) instead of raw protocol reasons. AgentsViewMode reconnects and refreshes on restarts but stops retrying after an intentional shutdown with sticky restart guidance.

Socket lifecycle is hardened with proper-lockfile, inode-based identity checks, a post-shutdown cleanup grace, and shutdownDaemonAndWait treating accepted shutdowns as gone only after the socket is reclaimable (including crash-left stale sockets).

A small generate-models tweak refreshes Prime Inference alias contextWindow / maxTokens from the live catalog when merging snapshot models.

^{Reviewed by Cursor Bugbot for commit 4d309ba. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Preserve daemon sessions across self-updates by reconnecting and restoring active sessions

• When a daemon restarts for a self-update, DaemonAgentConnection now automatically reconnects the transport and re-attaches to the previous session, emitting a session_replaced event on success and a terminal closed event with recovery guidance after a 120s timeout.
• The daemon broadcasts a new daemon_closing outbound message (with reason 'update' or 'shutdown') before closing, allowing clients to distinguish intentional shutdowns from crashes.
• DaemonSocketClosedError carries the close reason through the error chain so callers can gate reconnection logic on getDaemonSocketCloseReason().
• Agents View (AgentsViewMode) now auto-reconnects to the daemon for up to 120s on disconnection; on a clean 'shutdown' reason it stops retrying, shows a sticky error, and clears the session list.
• Socket cleanup in daemon-socket.ts is now lock-coordinated and identity-checked to avoid unlinking a replacement daemon's socket during concurrent restarts.
• Behavioral Change: closed events from DaemonAgentConnection now carry formatted user-facing messages with session ID, file, and diagnostic log path instead of raw protocol reasons.

^{Macroscope summarized 4d309ba.}